Mobile device management profile distribution

ABSTRACT

Methods, systems, and apparatus, including computer programs encoded on computer storage media, for automated mobile device management profile distribution. One of the methods includes receiving a first request for access to a first network resource from a client device, the first network resource corresponding to one of a plurality of restricted resources accessible only by devices enrolled with a mobile device management system, determining that the client device is not enrolled with the mobile device management system, preventing the client device access to the first network resource, providing to the client device a redirect to a mobile device management resource that is different from the first network resource, providing instructions for presentation of a user interface to the client device, and enrolling the client device with the mobile device management system, the enrolling comprising providing a copy of the mobile device management profile to the client device.

TECHNICAL FIELD

This specification relates to systems and techniques that facilitateinstallation of mobile device management profiles.

BACKGROUND

Mobile device management functionality can include over the airdistribution of data and software applications, and configuration ofmobile device settings. Mobile device management can be used for bothorganization owned and employee owned devices.

The use of mobile device management by an organization can reduce riskand support costs by enforcing policies on the mobile devices thataccess the organizations data. For example, mobile device managementprofiles can enforce the use of password protection on mobile devices.

SUMMARY

In general, one aspect of the subject matter described in thisspecification can be embodied in methods that include the actions ofreceiving a first request for access to a first network resource from aclient device, the first network resource corresponding to one of aplurality of restricted resources accessible only by devices enrolledwith a mobile device management system, determining that the clientdevice is not enrolled with the mobile device management system,preventing, based on determining that the client device is not enrolledwith the mobile device management system, the client device access tothe first network resource, providing to the client device, based ondetermining that the client device is not enrolled with the mobiledevice management system, a redirect to a mobile device managementresource that is different from the first network resource, providinginstructions for presentation of a user interface to the client device,the provided instructions relating to the mobile device managementresource and comprising a user notification regarding a mobile devicemanagement profile, and enrolling the client device with the mobiledevice management system, the enrolling comprising providing a copy ofthe mobile device management profile to the client device. Otherimplementations of this aspect include corresponding computer systems,apparatus, and computer programs recorded on one or more computerstorage devices, each configured to perform the actions of the methods.A system of one or more computers can be configured to performparticular operations or actions by virtue of having software, firmware,hardware, or a combination of them, installed on the system that inoperation causes or cause the system to perform the actions. One or morecomputer programs can be configured to perform particular operations oractions by virtue of including instructions that, when executed by dataprocessing apparatus, cause the apparatus to perform the actions.

The foregoing and other implementations can each optionally include oneor more of the following features, alone or in combination. Inparticular, one implementation may include all the following features incombination. The method may further comprise receiving a second requestfor access to a second network resource from the client device, thesecond request received prior to the first request and the secondnetwork resource corresponding to one of a plurality of unrestrictedresources accessible by devices not enrolled with the mobile devicemanagement system, and allowing the client device access to the secondnetwork resource.

In some implementations, the method further comprises receiving a secondrequest for access to a second network resource from the client device,the second network resource corresponding to one of the plurality ofrestricted resources, determining whether the client device is enrolledwith the mobile device management system, and allowing the client deviceaccess to the second network resource based on determining that theclient device is enrolled with the mobile device management system. Themethod may further comprise determining whether the mobile devicemanagement profile has been deactivated on the client device, andun-enrolling the client device from the mobile device management systembased on determining that the mobile device management profile has beenremoved from the client device, the un-enrolling preventing the clientdevice from accessing the plurality of restricted resources. Theplurality of restricted resources may comprise resources managed by anorganization that uses the mobile device management system. Theplurality of restricted resources may comprise public network resources.

In some implementations, determining that the client device is notenrolled with the mobile device management system may comprisedetermining whether a heartbeat signal has been received within apredetermined period of time, and determining that the client device isnot enrolled with the mobile device management system based ondetermining that the heartbeat signal has not been received within thepredetermined period of time. Determining that the client device is notenrolled with the mobile device management system may comprisedetermining whether a device identifier associated with the clientdevice is categorized as being enrolled with the mobile devicemanagement system, and determining that the client device is notenrolled with the mobile device management system based on determiningthat the device identifier associated with the client device is notcategorized as being enrolled with the mobile device management system.

In some implementations, determining that the client device is notenrolled with the mobile device management system comprises determiningwhether one or more network settings of the client device indicate thatthe client device is enrolled with the mobile device management system,and determining that the client device is not enrolled with the mobiledevice management system is based on determining that one or morenetwork settings of the client device indicate that the client device isnot enrolled with the mobile device management system. The networksettings may comprise a proxy server setting. Determining whether theone or more network settings of the client device indicate that theclient device is enrolled with the mobile device management system maycomprise determining whether the first request to access the firstresource was received by a predetermined proxy server. Determining thatone or more network settings of the client device indicate that theclient device is not enrolled with the mobile device management systemmay comprise determining that the first request to access the firstresource was not received by the predetermined proxy server. The networksettings may comprise a network connection setting. Determining whetherthe one or more network settings of the client device indicate that theclient device is enrolled with the mobile device management system maycomprise determining whether the client device is connected to anon-compliant network, the non-compliant network providing access to theplurality of unrestricted resources and not providing access to any ofthe plurality of restricted resources. Determining that one or morenetwork settings of the client device indicate that the client device isnot enrolled with the mobile device management system comprisesdetermining that the client device is connected to a non-compliantnetwork.

In some implementations, the instructions comprise instructions forpresentation of an agreement to enroll the client device with the mobiledevice management system, and enrolling the client device with themobile device management system comprises receiving input from theclient device indicating acceptance of the agreement, wherein the clientdevice is enrolled with the mobile device management system in responseto receiving the input from the client device. The instructions maycomprise information about access to the first network resource.

The subject matter described in this specification may be implemented invarious implementations to realize one or more of the followingpotential advantages. In some implementations, a determination ofwhether a client device is enrolled with a mobile device managementsystem and distribution of a mobile device management profile to theclient device automates the enrollment of the client device with themobile device management system. In some implementations, automatedmobile device management enrollment facilitates the installation of amobile device management profile on a client device without a manualnavigation of the client device to a resource associated with theprofile and without an administrator manually installing the profile onthe client device.

Details of one or more implementations are set forth in the accompanyingdrawings and the description below. Other features, aspects, andpotential advantages will become apparent from the description, thedrawings, and the claims.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is an example of a network system configured to

FIG. 2 is a block diagram of an environment in which

FIG. 3 is a flow diagram of a process for

FIG. 4 is a block diagram of computing devices that may be used toimplement the systems and methods described in this document.

Like reference numbers and designations in the various drawings indicatelike elements.

DETAILED DESCRIPTION

Some employees bring their own device with them to work to gain accessto the resources of the organization for which the employee works. Theresources may include both restricted resources, such as confidentialdocuments, and unrestricted resources, such as public documents.

Some organizations require that employees have a mobile devicemanagement profile installed on their personal devices before theorganizations allow the devices access to resources, e.g., therestricted resources. For example, an organization's network may preventa device from accessing restricted network resources, while the deviceuses the organization's network, until a copy of a mobile devicemanagement profile is installed on the device. Once the mobile devicemanagement profile is installed, the device will gain access to thepreviously restricted resources.

To facilitate installation of the mobile device management profile on anemployee's device, the organization's network determines whether themobile device management profile is installed on the device when thedevice connects to the network. If the network determines that theprofile is installed on the device, the network allows the device toaccess any resources available to an operator of the device, e.g., basedon permissions of the operator. If, however, the network determines thatthe profile is not installed on the device, the network directs thedevice to present a page associated with the mobile device managementprofile to allow the operator of the device to request that a copy ofthe profile be installed on the device.

FIG. 1 is an example of a network system 100 configured to provide aclient device 102 with a redirect to a device management resource. Whenthe client device 102 does not have a device management profileinstalled and requests access to a restricted resource, the networksystem 100 prevents the client device 102 from accessing the restrictedresource. The network system 100 redirects the client device 102 to thedevice management resource, e.g., a web page, that includes informationabout the device management profile to allow an operator of the clientdevice 102 to request that the device management profile be installed onthe client device 102 so that the client device 102 will receive accessto the restricted resource.

At time T₁, the client device 102 accesses a network 104 of the networksystem 100 and requests access to one of a plurality of unrestrictedresources 106. For example, the client device 102 requests access to aweb page hosted by the network system 100 that contains informationabout the organization that manages the network system 100. In someexamples, an operator of the client device 102 uses the client device102 to request information about the company for which the operatorworks.

The network system 100 allows the client device 102 to receive a copy ofthe requested unrestricted resource. For example, the network system 100provides the client device 102 with a copy of the requested web page.

The client device 102, at time T₂, requests access to one of a pluralityof restricted resources 108. For example, the client device 102 requestsaccess to a confidential document of the organization that employs theoperator of the client device 102. In some examples, when the clientdevice 102 requests access to an Internet resource, the network system100 determines that the requested Internet resource is one of therestricted resources 108 and prevents the client device 102 fromaccessing the Internet resource. For example, the restricted resources108 may include all Internet resources, e.g., Internet web pages, or asubset of Internet resources.

The network system 100 provides the client device 102 with a redirectfor a device management resource different from the requested restrictedresource at time T₃. For example, the client device 102 receives theredirect and requests the device management resource from the networksystem 100. The device management resource may include instructions forthe presentation of a user interface on the client device 102 wherepresentation of the user interface informs the operator of the clientdevice 102 that the client device 102 must be enrolled with the networksystem 100 before the client device 102 can access the requestedrestricted resource.

The client device 102 receives, at time T₄, the user interfaceinstructions and presents the user interface to the operator of theclient device 102. The operator of the client device 102 interacts withthe user interface, e.g., by selecting a “proceed with enrollment”option, and the client device requests a device management profile 110from the network system 100.

At time T₅, the client device 102 receives a copy of the devicemanagement profile 110 a and installs the copy of the device managementprofile 110 a in a memory of the client device 102. The installation ofthe copy of the device management profile 110 a, for example, configuresone or more settings of the client device 102 to allow the client device102 to access the restricted resources 108. For example, the devicemanagement profile 110 a configures one or more network settings, suchas a proxy setting or a wireless network setting, of the client device102 to allow the client device to access some of the restrictedresources 108, e.g., based on permissions of the operator of the clientdevice 102.

In some implementations, the installation of the copy of the devicemanagement profile 110 a on the client device 102 applies one or morerestrictions on the client device 102. For example, the devicemanagement profile 110 a may prevent the installation of potentiallyunsafe applications on the client device 102 and/or may remove anypotentially unsafe applications from the client device 102 after thedevice management profile 110 a is initially installed.

In some implementations, an operator of the client device 102 maydeactivate the device management profile 110 a at time T₆. For example,the operator may disable or uninstall the device management profile 110a. Deactivation of the device management profile 110 a may allow theoperator of the client device 102 to install any application on theclient device 102, whether or not an application is identified aspotentially unsafe, but prevents the client device 102 from accessingany of the restricted resources 108. For example, when the client device102 requests access to one of the restricted resources 108 after timeT₆, the network system 100 determines that the device management profile110 a has been deactivated and prevents the client device 102 fromaccessing the requested restricted resource. When the operator of theclient device 102 deactivates the device management profile 110 a, allpayloads, settings, and/or policies that were distributed to the clientdevice 102 during installation of the device management profile 110 aare removed from the client device 102.

In some implementations, the unrestricted resources 106 only include thedevice management resource. For example, when the client device 102 doesnot have the device management profile 110 a installed, the networksystem 100 prevents the client device 102 from accessing any networkresources, e.g., resources of the organization managing the networksystem 100 and Internet resources, except for the device managementresource. When the client device 102 requests access to any resource,except the device management resource, the network system 100 providesthe client device 102 with the redirect for the device managementresource and does not allow the client device 102 to access therequested resource until the copy of the device management profile 110 ais installed on the client device 102.

The client device 102 may include personal computers, mobilecommunication devices, and other devices that can send and receive dataover the network 104. The network 104, such as a local area network(LAN), wide area network (WAN), the Internet, or a combination thereof,connects the client device 102, the unrestricted resources 106, and therestricted resources 108. Some examples of resources, restricted and/orunrestricted, include web pages, network printers, file servers, andscanners.

In some implementations, the time periods T₁, T₂, T₃, T₄, T₅, and T₆ canoverlap. For example, operations performed in time period T₁, can beperformed in parallel with operations performed in time period T₂. Theclient device 102 could, for example, request the unrestricted resourceduring time T₁ and then request the restricted resource during time T₂while waiting to receive the unrestricted resource. In some examples,the client device 102 may receive the redirect and request the mobiledevice management resource during time T₃, and then request anunrestricted resource during time T₁. Further, the client device 102 maycontinue to request and/or receive unrestricted resources whilereceiving the user interface during time T₄ and receiving the mobiledevice management profile during time T₅. In some examples, the clientdevice 102 may request an unrestricted resource during time T₁ afterdeactivating the device management profile 110 a during time T₆.

FIG. 2 is a block diagram of an environment 200 in which an accesscontrol system 202 determines whether a client device 204 is enrolledwith a mobile device management system 206. When the client device 204first connects to a network 208 and requests a resource, such as one ofa plurality of unrestricted resources 210 or one of a plurality ofrestricted resources 212, the access control system 202 determineswhether the client device 204 is enrolled with the mobile devicemanagement system 206 and prevents or allows access to the requestedresource accordingly.

For example, when the client device 204 requests access to one of theunrestricted resources 210, such as a home page for the organizationthat manages the network 208, the access control system 202 allows theclient device 204 to access the requested unrestricted resource.

If, however, the client device 204 requests access to one of therestricted resources 212, such as a patient's medical record or anotherconfidential document of the organization, the access control system 202determines whether the client device 204 is enrolled with the mobiledevice management system 206 and prevents or allows access to therequested restricted resource accordingly. For example, if the clientdevice 204 is not currently enrolled with the mobile device managementsystem 206, then the access control system 202 prevents the clientdevice 204 from accessing the requested restricted resource.

In some examples, the access control system 202 provides the clientdevice 204 with a redirect, such as a hypertext transfer protocol (HTTP)redirect, for a mobile device management resource different from therequested restricted resource. For example, the mobile device managementresource may be one of the unrestricted resources 210.

Upon accessing the mobile device management resource, the client device204 may receive instructions for receiving a mobile device managementprofile 214 from the mobile device management system 206 and installinga copy of the mobile device management profile 214 as one of a pluralityof device profiles 216 of the client device 204. The mobile devicemanagement profile 214 may configure one or more settings of the clientdevice 204 and/or of the other device profiles 216 to allow the clientdevice 204 to access the restricted resources 212.

In some implementations, the mobile device management profile 214configures one or more network settings of the client device 204 toindicate that the client device 204 is enrolled with the mobile devicemanagement system 206. For example, the mobile device management profile214 may configure a proxy setting so that the client device 204 sendsresource requests to a proxy server 218 in the environment 200. Theaccess control system 202 may then determine whether a request from theclient device 204 to access one of the restricted resources 212 wasreceived by the proxy server 218 as an indication of whether the clientdevice 204 is enrolled with the mobile device management system 206.

If the request for the restricted resource is received by the proxyserver 218, the access control system 202 determines that the clientdevice 204 is enrolled with the mobile device management system 206, hasa copy of the mobile device management profile 214 installed in amemory, and should be allowed to access the requested restrictedresource. If, however, the access control system 202 determines that therequest was not received by the proxy server 218, the access controlsystem 202 determines that the client device 204 is not enrolled withthe mobile device management system 206 and prevents the client device204 from accessing the requested restricted resource.

In some implementations, when the network settings include a networkconnection setting, the access control system 202 determines whether theclient device 204 is enrolled with the mobile device management system206 based on the network with which the client device 204 connects. Forexample, the access control system 202 may determine whether the clientdevice 204 is connected to a non-compliant network 220 or a compliantnetwork 222 and prevent or allow, respectively, access to the restrictedresources 212. For example, when the client device 204 enrolls with themobile device management system 206, the mobile device managementprofile 214 may configure one or more settings for access to a compliantwireless network such that, upon determining that the client device 204is connected to the compliant wireless network, the access controlsystem 202 allows the client device 204 access to a restricted resource.If the access control system 202 determines that the client device 204is connected to a non-compliant wireless network, the access controlsystem 202 prevents the client device 204 from accessing any of therestricted resources 212 and allows the client device 204 to access theunrestricted resources 210.

In some implementations, the non-compliant network 220 and the compliantnetwork 222 are part of the same network. For example, when the clientdevice 204 connects to the network 208 and is not enrolled with themobile device management system 206, the client device 204 may beassigned a first internet protocol address from a first range ofinternet protocol addresses associated with the non-compliant network220. When the client device 204 enrolls with the mobile devicemanagement system 206, the client device 204 is assigned a secondinternet protocol address from a second range of internet protocoladdresses associated with the compliant network 222. In theseimplementations, the access control system 202 determines whether theclient device 204 is enrolled with the mobile device management system206 based on the current internet protocol address assigned to theclient device 204.

In some implementations, the non-compliant network 220 is an unsecurednetwork and the compliant network 222 is a secured network. For example,data transferred across the compliant network 222 may be encrypted.

In some implementations, when the mobile device management profile isdeactivated on the client device 204, the environment 200 automaticallyremoves the access of the client device 204 to the restricted resources212 at substantially the same time that the mobile device managementprofile is deactivated. For example, when the mobile device managementprofile configures the access of the client device 204 to the compliantnetwork 222, e.g., a compliant wireless network, and the mobile devicemanagement profile on the client device 204 is deactivated, thecredentials that allow the client device 204 to connect to the compliantnetwork 222 are removed and the client device 204 connects to thenon-compliant network 220, e.g., based on the settings of the clientdevice 204, and is unable to access the restricted resources 212.

In some implementations, when the mobile device management profile onthe client device 204 is deactivated, the proxy settings for the proxyserver 218 are removed from the client device 204. For example, when theaccess control system 202 determines that the client device 204 isenrolled with the mobile device management system 206 based on whether aresource request from the client device 204 was received by the proxyserver 218 and an operator of the client device 204 deactivates, e.g.,disables or uninstalls, the copy of the mobile device management profileon the client device 204, the proxy settings for the proxy server 218are automatically removed from the client device 204 so that laterresource requests made by the client device 204 are not sent to theproxy server 218. This may allow the access control system 202 todetermine at substantially the same time the mobile device managementprofile is deactivated on the client device 204, that the client device204 is no longer enrolled with the mobile device management system 206.

In some implementations, the mobile device management profile 214configures the client device 204 to send a heartbeat signal to themobile device management system 206 while the mobile device managementprofile 214 is installed and enabled on the client device 204. Forexample, upon installation of the mobile device management profile 214,the client device 204 periodically sends a signal to the mobile devicemanagement system 206 where the signal indicates that the client device204 has the mobile device management profile 214 installed and that theclient device 204 is enrolled with the mobile device management system206.

When an operator of the client device 204 disables or uninstalls themobile device management profile 214 from the client device 204, theclient device 204 no longer sends the heartbeat signal to the mobiledevice management system 206, indicating that the client device 204 isno longer enrolled with the mobile device management system 206. Inthese implementations, the access control system 202 determines whetherthe client device 204 is enrolled with the mobile device managementsystem 206 based on the receipt of the heartbeat signal by the mobiledevice management system 206 from the client device 204. For example,the heartbeat signal may include an identifier of the client device 204.

In some implementations, the mobile device management system 206 recordsa device identifier of the client device 204 when the client device 204enrolls with the mobile device management system 206. For example, themobile device management system 206 stores a media access controladdress of the client device 204 when the mobile device managementprofile 214 is installed on the client device 204 to indicate that theclient device 204 is enrolled with the mobile device management system206. When the mobile device management profile 214 is deactivated on theclient device 204, the mobile device management system 206 may receive amessage from the client device 204 indicating the deactivation of themobile device management profile 214 and update data associated with theclient device's 204 media access control address to indicate that theclient device 204 is no longer enrolled with the mobile devicemanagement system 206.

In some examples, the access control system 202 and/or the mobile devicemanagement system 206 determine whether the client device 204 isenrolled with the mobile device management system 206 based on a recordin a memory of the mobile device management system 206, e.g., a databaserecord. For example, the record may indicate whether or not the clientdevice 204 is enrolled with the mobile device management system 206,e.g., where the record includes an identifier of the client device 204.

The access control system 202 and/or the mobile device management system206 may use any appropriate algorithm to determine whether the clientdevice 204 is enrolled with the mobile device management system 206 andto monitor the enrollment of the client device 204 with the mobiledevice management system 206.

In some implementations, the access control system 202 and the mobiledevice management system 206 are part of the same system. For example, asingle server may include the access control system 202 and the mobiledevice management system 206.

In some implementations, the proxy server 218 is part of the same systemas the access control system 202 and/or the mobile device managementsystem 206. For example, the same server may host the access controlsystem 202 and the proxy server 218.

The client device 204 may include personal computers, mobilecommunication devices, and other devices that can send and receive dataover the network 208. The network 208, such as a local area network(LAN), wide area network (WAN), the Internet, or a combination thereof,connects the access control system 202, the client device 204, themobile device management system 206, the unrestricted resources 210, therestricted resources 212, and the proxy server 218.

FIG. 3 is a flow diagram of a process 300 for providing a client devicewith a mobile device management profile. For example, the process 300can be used by the access control system 202 from the environment 200.In some implementations, one or more steps of the process 300 may beperformed by another component of the environment 200, such as themobile device management system 206.

The process receives a first request for access to a first networkresource from a client device (302). The first network resourcecorresponds to one of a plurality of unrestricted resources accessibleby devices not enrolled with a mobile device management system. Forexample, the access control system receives a copy of a request for anunrestricted resource from the client device.

The access control system allows the client device access to the firstnetwork resource. For example, the access control system does not blockthe client device's access to the requested unrestricted resource. Theaccess control system may use any appropriate algorithm to allow and/orblock access to unrestricted and restricted resources.

The process receives a second request for access to a second networkresource from the client device (304). The second network resourcecorresponds to one of a plurality of restricted resources accessibleonly by devices enrolled with the mobile device management system. Forexample, the access control system receives a request for a restrictedresource, such as a confidential document, an internal organizationfile, or a web page, from the client device.

In some implementations, the plurality of restricted resources comprisesresources managed by an organization that uses the mobile devicemanagement system and/or the access control system. Some examples ofrestricted resources managed by an organization include confidentialdocuments, patient files, internal memoranda, intranet web pages,accounting files, internal educational files, human resource files,organization printers, and organization scanners, among other types ofresources managed by the organization.

In some implementations, the plurality of restricted resources comprisespublic network resources. For example, the public network resources mayinclude one or more Internet resources. Some examples of restrictedpublic network resources include public web pages, file transferprotocol files, instant messaging resources, and chat room resources,among other types of network resources.

The process determines that the client device is not enrolled with themobile device management system (306). For example, the access controlsystem or the mobile device management system determine that the clientdevice is not sending a heartbeat signal to the mobile device managementsystem, that an identifier of the client device does not indicate thatthe client device is enrolled with the mobile device management system,and/or that one or more network settings, such as a proxy server settingor a network connection setting, do not indicate that the client deviceis enrolled with the mobile device management system.

The process prevents the client device from accessing the second networkresource (308). For example, the access control system prevents theclient device from accessing the second network resource based ondetermining that the client device is not enrolled with the mobiledevice management system.

The process provides a redirect to a mobile device management resource(310). For example, the access control system provides the client devicewith the redirect to the mobile device management resource, differentfrom the first network resource and the second network resource, basedon determining that the client device is not enrolled with the mobiledevice management system.

The process provides instructions for presentation of a user interfaceto the client device (312). The provided instructions relate to themobile device management resource and comprise a user notificationregarding a mobile device management profile. For example, the clientdevice receives the redirect for the mobile device management resourceand the access control system or the mobile device management system, inresponse to the client device's request for the mobile device managementresource, provides the instructions to the client device.

In some implementations, the user interface includes a request forcredentials from an operator of the client device. For example, the userinterface includes user interface elements that request a username andpassword for the operator of the client device.

In some implementations, the instructions include instructions forpresentation of an agreement to enroll the client device with the mobiledevice management system. For example, the agreement indicates that amobile device management profile will be installed on the client deviceand any restrictions associated with the installation of the mobiledevice management profile.

In some implementations, the instructions comprise information aboutaccess to the second network resource. For example, the instructions mayindicate that the client device will be redirected to the second networkresource after the mobile device management profile is installed on theclient device or that the client device will have access to the secondnetwork resource after the mobile device management profile is installedon the client device.

The process enrolls the client device with the mobile device managementsystem by providing the client device with a mobile device managementprofile (314). For example, the mobile device management system providesthe client device with a copy of the mobile device management profileand, upon installation of the copy of the mobile device managementprofile on the client device, the mobile device management system maystore a record in memory, e.g., in a database, indicating that theclient device is enrolled with the mobile device management system.

In some implementations, upon installation on the client device, themobile device management profile sends a message to the mobile devicemanagement system indicating that installation was successful. Forexample, when the mobile device management system only stores a recordwith an identifier of the client device to indicate that the clientdevice is enrolled with the mobile device management system and themobile device management profile does not adjust a network setting onthe client device or send a heartbeat signal to the mobile devicemanagement system, the mobile device management system does not createthe record until the mobile device management system receives aninstallation successful message from the mobile device managementprofile.

In some implementations, enrolling the client device with the mobiledevice management system includes receiving input from the client deviceindicating acceptance of the agreement, wherein the client device isenrolled with the mobile device management system in response toreceiving the input from the client device. For example, the mobiledevice management system does not provide the mobile device managementprofile to the client device or enroll the client device, e.g., allowthe client device to access restricted resources, if an operator of theclient device does not accept the agreement.

The process allows the client device access to a plurality of restrictedresources (316). For example, the access control system receives a thirdrequest for access to a third network resource from the client device,the third network resource corresponding to one of the plurality ofrestricted resources, and determines whether the client device isenrolled with the mobile device management system. The access controlsystem allows the client device access to the third network resourcebased on determining that the client device is enrolled with the mobiledevice management system.

In some implementations, the third network resource is the same resourceas the second network resource. For example, after enrolling with themobile device management system, the client device may request thesecond network resource and the access control system, after receivingthe request, would allow the client device to access the second networkresource.

In some implementations, the third network resource is a differentresource from the second network resource. For example, after enrollingwith the mobile device management system, the client device may requestaccess to the third network resource.

The process determines whether the mobile device management profile hasbeen deactivated on the client device (318). For example, the accesscontrol system or the mobile device management system determines whetherthe mobile device management profile has been disabled or uninstalled onthe client device. In some examples, an operator of the client devicemay disable the device management profile in order to install anapplication that the mobile device management profile prevented frombeing installed.

The process un-enrolls the client device from the mobile devicemanagement system (320). For example, the mobile device managementsystem determines that the client device is no longer sending theheartbeat signal to the mobile device management system and un-enrollsthe client device from the mobile device management system. In someexamples, the mobile device management system receives a message fromthe client device that indicates that the mobile device managementprofile has been deactivated. In some implementations, when the mobiledevice management profile is deactivated, one or more network settings,such as a network connection setting or a proxy server setting, on theclient device are restored to an original value and the network to whichthe client device connects indicates that the client device is or shouldbe un-enrolled from the mobile device management system.

The process prevents the client device from accessing the restrictedresources (322). For example, upon determining that the client device isno longer enrolled with the mobile device management system, the accesscontrol system prevents the client from accessing any of the restrictedresources.

The order of steps in the process 300 described above is illustrativeonly, and providing the client device with the mobile device managementprofile can be performed in different orders. For example, the accesscontrol system may determine whether the client device is enrolled withthe mobile device management system, e.g., perform step 306, when theclient device first connects to the network and then receive the secondrequest for access to the second network resource, e.g., perform step304.

In some implementations, the process 300 can include additional steps,fewer steps, or some of the steps can be divided into multiple steps.For example, the access control system may provide the client devicewith the redirect when the client device connects to the network andupon determining that the client device is not enrolled with the mobiledevice management system, e.g., without receiving the second request foraccess to the second network resource. For example, the access controlsystem may perform steps 306 and 310 without performing steps 304 and308.

In some implementations, the access control system prevents the clientdevice from accessing the restricted resources, e.g., performs step 322,without un-enrolling the client device, e.g., performing step 320. Forexample, if the client device previously un-enrolled from the mobiledevice management system, the access control system may determine thatthe client device is not enrolled, e.g., perform step 318, and preventthe client device from accessing the restricted resources, e.g., performstep 322.

In some implementations, the process 300 includes steps 304 through 314and does not include the other steps in the process, e.g., steps 302 and316 through 322. For example, the access control system may receive therequest for the restricted resource and later enroll the client devicewith the mobile device management system without receiving a request foran unrestricted resource, without allowing the client device to accessone or more restricted resources, and without determining whether themobile device management profile has been deactivate.

FIG. 4 is a block diagram of computing devices 400, 450 that may be usedto implement the systems and methods described in this document, aseither a client or as a server or plurality of servers. Computing device400 is intended to represent various forms of digital computers, such aslaptops, desktops, workstations, personal digital assistants, servers,blade servers, mainframes, and other appropriate computers. Computingdevice 450 is intended to represent various forms of mobile devices,such as personal digital assistants, cellular telephones, smartphones,and other similar computing devices. Additionally computing device 400or 450 can include Universal Serial Bus (USB) flash drives. The USBflash drives may store operating systems and other applications. The USBflash drives can include input/output components, such as a wirelesstransmitter or USB connector that may be inserted into a USB port ofanother computing device. The components shown here, their connectionsand relationships, and their functions, are meant to be exemplary only,and are not meant to limit implementations of the inventions describedand/or claimed in this document.

Computing device 400 includes a processor 402, memory 404, a storagedevice 406, a high speed interface 408 connecting to memory 404 and highspeed expansion ports 410, and a low speed interface 412 connecting tolow speed bus 414 and storage device 406. Each of the components 402,404, 406, 408, 410, and 412, are interconnected using various busses,and may be mounted on a common motherboard or in other manners asappropriate. The processor 402 can process instructions for executionwithin the computing device 400, including instructions stored in thememory 404 or on the storage device 406 to display graphical informationfor a GUI on an external input/output device, such as display 416coupled to high speed interface 408. In other implementations, multipleprocessors and/or multiple buses may be used, as appropriate, along withmultiple memories and types of memory. Also, multiple computing devices400 may be connected, with each device providing portions of thenecessary operations (e.g., as a server bank, a group of blade servers,or a multi-processor system).

The memory 404 stores information within the computing device 400. Inone implementation, the memory 404 is a volatile memory unit or units.In another implementation, the memory 404 is a non-volatile memory unitor units. The memory 404 may also be another form of computer-readablemedium, such as a magnetic or optical disk.

The storage device 406 is capable of providing mass storage for thecomputing device 400. In one implementation, the storage device 406 maybe or contain a computer-readable medium, such as a floppy disk device,a hard disk device, an optical disk device, or a tape device, a flashmemory or other similar solid state memory device, or an array ofdevices, including devices in a storage area network or otherconfigurations. A computer program product can be tangibly embodied inan information carrier. The computer program product may also containinstructions that, when executed, perform one or more methods, such asthose described above. The information carrier is a computer- ormachine-readable medium, such as the memory 404, the storage device 406,or memory on processor 402.

The high speed controller 408 manages bandwidth-intensive operations forthe computing device 400, while the low speed controller 412 manageslower bandwidth-intensive operations. Such allocation of functions isexemplary only. In one implementation, the high speed controller 408 iscoupled to memory 404, display 416 (e.g., through a graphics processoror accelerator), and to high speed expansion ports 410, which may acceptvarious expansion cards (not shown). In the implementation, low speedcontroller 412 is coupled to storage device 406 and low speed expansionport 414. The low speed expansion port, which may include variouscommunication ports (e.g., USB, Bluetooth, Ethernet, wireless Ethernet)may be coupled to one or more input/output devices, such as a keyboard,a pointing device, a scanner, or a networking device such as a switch orrouter, e.g., through a network adapter.

The computing device 400 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as astandard server 420, or multiple times in a group of such servers. Itmay also be implemented as part of a rack server system 424. Inaddition, it may be implemented in a personal computer such as a laptopcomputer 422. Alternatively, components from computing device 400 may becombined with other components in a mobile device (not shown), such asdevice 450. Each of such devices may contain one or more of computingdevice 400, 450, and an entire system may be made up of multiplecomputing devices 400, 450 communicating with each other.

Computing device 450 includes a processor 452, memory 464, aninput/output device such as a display 454, a communication interface466, and a transceiver 468, among other components. The device 450 mayalso be provided with a storage device, such as a microdrive or otherdevice, to provide additional storage. Each of the components 450, 452,464, 454, 466, and 468, are interconnected using various buses, andseveral of the components may be mounted on a common motherboard or inother manners as appropriate.

The processor 452 can execute instructions within the computing device450, including instructions stored in the memory 464. The processor maybe implemented as a chipset of chips that include separate and multipleanalog and digital processors. Additionally, the processor may beimplemented using any of a number of architectures. For example, theprocessor 402 may be a CISC (Complex Instruction Set Computers)processor, a RISC (Reduced Instruction Set Computer) processor, or aMISC (Minimal Instruction Set Computer) processor. The processor mayprovide, for example, for coordination of the other components of thedevice 450, such as control of user interfaces, applications run bydevice 450, and wireless communication by device 450.

Processor 452 may communicate with a user through control interface 458and display interface 456 coupled to a display 454. The display 454 maybe, for example, a TFT (Thin-Film-Transistor Liquid Crystal Display)display or an OLED (Organic Light Emitting Diode) display, or otherappropriate display technology. The display interface 456 may compriseappropriate circuitry for driving the display 454 to present graphicaland other information to a user. The control interface 458 may receivecommands from a user and convert them for submission to the processor452. In addition, an external interface 462 may be provide incommunication with processor 452, so as to enable near areacommunication of device 450 with other devices. External interface 462may provide, for example, for wired communication in someimplementations, or for wireless communication in other implementations,and multiple interfaces may also be used.

The memory 464 stores information within the computing device 450. Thememory 464 can be implemented as one or more of a computer-readablemedium or media, a volatile memory unit or units, or a non-volatilememory unit or units. Expansion memory 474 may also be provided andconnected to device 450 through expansion interface 472, which mayinclude, for example, a SIMM (Single In Line Memory Module) cardinterface. Such expansion memory 474 may provide extra storage space fordevice 450, or may also store applications or other information fordevice 450. Specifically, expansion memory 474 may include instructionsto carry out or supplement the processes described above, and mayinclude secure information also. Thus, for example, expansion memory 474may be provide as a security module for device 450, and may beprogrammed with instructions that permit secure use of device 450. Inaddition, secure applications may be provided via the SIMM cards, alongwith additional information, such as placing identifying information onthe SIMM card in a non-hackable manner.

The memory may include, for example, flash memory and/or NVRAM memory,as discussed below. In one implementation, a computer program product istangibly embodied in an information carrier. The computer programproduct contains instructions that, when executed, perform one or moremethods, such as those described above. The information carrier is acomputer- or machine-readable medium, such as the memory 464, expansionmemory 474, or memory on processor 452 that may be received, forexample, over transceiver 468 or external interface 462.

Device 450 may communicate wirelessly through communication interface466, which may include digital signal processing circuitry wherenecessary. Communication interface 466 may provide for communicationsunder various modes or protocols, such as GSM voice calls, SMS, EMS, orMMS messaging, CDMA, TDMA, PDC, WCDMA, CDMA2000, or GPRS, among others.Such communication may occur, for example, through radio-frequencytransceiver 468. In addition, short-range communication may occur, suchas using a Bluetooth, WiFi, or other such transceiver (not shown). Inaddition, GPS (Global Positioning System) receiver module 470 mayprovide additional navigation- and location-related wireless data todevice 450, which may be used as appropriate by applications running ondevice 450.

Device 450 may also communicate audibly using audio codec 460, which mayreceive spoken information from a user and convert it to usable digitalinformation. Audio codec 460 may likewise generate audible sound for auser, such as through a speaker, e.g., in a handset of device 450. Suchsound may include sound from voice telephone calls, may include recordedsound (e.g., voice messages, music files, etc.) and may also includesound generated by applications operating on device 450.

The computing device 450 may be implemented in a number of differentforms, as shown in the figure. For example, it may be implemented as acellular telephone 480. It may also be implemented as part of asmartphone 482, personal digital assistant, or other similar mobiledevice.

Various implementations of the systems and techniques described here canbe realized in digital electronic circuitry, integrated circuitry,specially designed ASICs (application specific integrated circuits),computer hardware, firmware, software, and/or combinations thereof.These various implementations can include implementation in one or morecomputer programs that are executable and/or interpretable on aprogrammable system including at least one programmable processor, whichmay be special or general purpose, coupled to receive data andinstructions from, and to transmit data and instructions to, a storagesystem, at least one input device, and at least one output device.

These computer programs (also known as programs, software, softwareapplications or code) include machine instructions for a programmableprocessor, and can be implemented in a high-level procedural and/orobject-oriented programming language, and/or in assembly/machinelanguage. As used herein, the terms “machine-readable medium”“computer-readable medium” refers to any computer program product,apparatus and/or device (e.g., magnetic discs, optical disks, memory,Programmable Logic Devices (PLDs)) used to provide machine instructionsand/or data to a programmable processor, including a machine-readablemedium that receives machine instructions as a machine-readable signal.The term “machine-readable signal” refers to any signal used to providemachine instructions and/or data to a programmable processor.

To provide for interaction with a user, the systems and techniquesdescribed here can be implemented on a computer having a display device(e.g., a CRT (cathode ray tube) or LCD (liquid crystal display) monitor)for displaying information to the user and a keyboard and a pointingdevice (e.g., a mouse or a trackball) by which the user can provideinput to the computer. Other kinds of devices can be used to provide forinteraction with a user as well; for example, feedback provided to theuser can be any form of sensory feedback (e.g., visual feedback,auditory feedback, or tactile feedback); and input from the user can bereceived in any form, including acoustic, speech, or tactile input.

The systems and techniques described here can be implemented in acomputing system that includes a back end component (e.g., as a dataserver), or that includes a middleware component (e.g., an applicationserver), or that includes a front end component (e.g., a client computerhaving a graphical user interface or a Web browser through which a usercan interact with an implementation of the systems and techniquesdescribed here), or any combination of such back end, middleware, orfront end components. The components of the system can be interconnectedby any form or medium of digital data communication (e.g., acommunication network). Examples of communication networks include alocal area network (“LAN”), a wide area network (“WAN”), peer-to-peernetworks (having ad-hoc or static members), grid computinginfrastructures, and the Internet.

The computing system can include clients and servers. A client andserver are generally remote from each other and typically interactthrough a communication network. The relationship of client and serverarises by virtue of computer programs running on the respectivecomputers and having a client-server relationship to each other.

This document describes technologies that can be applied to a wide rangeof uses, which are designed and intended to be beneficial for all usersinvolved. However, some of the technologies described may be put toillegitimate, malicious, and even illegal ends by bad actors. This istrue with almost any technology, but there is often a greatersensitivity when a technology interacts with a user's security andprivate information. The described technologies all are designed tooperate in an environment and in a manner that respects the rights ofall users. As such, features such as user notification, opt-in andopt-out procedures, and privacy settings are available options to beused to ensure user security and privacy are respected.

Although a few implementations have been described in detail above,other modifications are possible. In addition, the logic flows depictedin the figures do not require the particular order shown, or sequentialorder, to achieve desirable results. Other steps may be provided, orsteps may be eliminated, from the described flows, and other componentsmay be added to, or removed from, the described systems. Accordingly,other implementations are within the scope of the following claims.

What is claimed is:
 1. A method performed by data processing apparatus,the method comprising: receiving a first request for access to a firstnetwork resource from a client device, the first network resourcecorresponding to one of a plurality of restricted resources accessibleonly by devices enrolled with a mobile device management system;determining whether the first request to access the first resourceincludes an address of a predetermined proxy server; determining thatthe first request to access the first resource does not include theaddress of the predetermined proxy server; determining that the clientdevice is not enrolled with the mobile device management system based ondetermining that the first request to access the first resource does notinclude the address of the predetermined proxy server; preventing, basedon determining that the client device is not enrolled with the mobiledevice management system, the client device from accessing the firstnetwork resource; providing to the client device, based on determiningthat the client device is not enrolled with the mobile device managementsystem, a redirect to a mobile device management resource that isdifferent from the first network resource; providing instructions forpresentation of a user interface to the client device, the providedinstructions relating to the mobile device management resource andcomprising a user notification regarding a mobile device managementprofile; and enrolling the client device with the mobile devicemanagement system, the enrolling comprising providing a copy of themobile device management profile to the client device.
 2. The method ofclaim 1, comprising: receiving a second request for access to a secondnetwork resource from the client device, the second request receivedprior to the first request and the second network resource correspondingto one of a plurality of unrestricted resources accessible by devicesnot enrolled with the mobile device management system; and allowing theclient device access to the second network resource.
 3. The method ofclaim 1, comprising: receiving a second request for access to a secondnetwork resource from the client device, the second network resourcecorresponding to one of the plurality of restricted resources;determining whether the client device is enrolled with the mobile devicemanagement system; and allowing the client device access to the secondnetwork resource based on determining that the client device is enrolledwith the mobile device management system.
 4. The method of claim 3,comprising: determining whether the mobile device management profile hasbeen deactivated on the client device; and un-enrolling the clientdevice from the mobile device management system based on determiningthat the mobile device management profile has been removed from theclient device, the un-enrolling preventing the client device fromaccessing the plurality of restricted resources.
 5. The method of claim3, wherein the plurality of restricted resources comprises resourcesmanaged by an organization that uses the mobile device managementsystem.
 6. The method of claim 3, wherein the plurality of restrictedresources comprises public network resources.
 7. The method of claim 1,wherein determining that the client device is not enrolled with themobile device management system comprises: determining whether aheartbeat signal has been received within a predetermined period oftime; and determining that the client device is not enrolled with themobile device management system based on determining that the heartbeatsignal has not been received within the predetermined period of time. 8.The method of claim 1, wherein determining that the client device is notenrolled with the mobile device management system comprises: determiningwhether a device identifier associated with the client device iscategorized as being enrolled with the mobile device management system;and determining that the client device is not enrolled with the mobiledevice management system based on determining that the device identifierassociated with the client device is not categorized as being enrolledwith the mobile device management system.
 9. The method of claim 1,wherein: the instructions comprise instructions for presentation of anagreement to enroll the client device with the mobile device managementsystem; and enrolling the client device with the mobile devicemanagement system comprises receiving input from the client deviceindicating acceptance of the agreement, wherein the client device isenrolled with the mobile device management system in response toreceiving the input from the client device.
 10. The method of claim 1,wherein determining that the client device is not enrolled with themobile device management system comprises: determining whether theclient device is connected to a non-compliant network, the non-compliantnetwork providing access to a plurality of unrestricted resources andnot providing access to any of the plurality of restricted resources;and determining that the client device is not enrolled with the mobiledevice management system based on determining that the client device isconnected to the non-compliant network.
 11. A non-transitory computerstorage medium encoded with instructions that, when executed by one ormore computers, cause the one or more computers to perform operationscomprising: receiving a first request for access to a first networkresource from a client device, the first network resource correspondingto one of a plurality of restricted resources accessible only by devicesenrolled with a mobile device management system; determining whether thefirst request to access the first resource includes an address of apredetermined proxy server; determining that the first request to accessthe first resource does not include the address of the predeterminedproxy server; determining that the client device is not enrolled withthe mobile device management system based on determining that the firstrequest to access the first resource does not include the address of thepredetermined proxy server; preventing, based on determining that theclient device is not enrolled with the mobile device management system,the client device from accessing the first network resource; providingto the client device, based on determining that the client device is notenrolled with the mobile device management system, a redirect to amobile device management resource that is different from the firstnetwork resource; providing instructions for presentation of a userinterface to the client device, the provided instructions relating tothe mobile device management resource and comprising a user notificationregarding a mobile device management profile; and enrolling the clientdevice with the mobile device management system, the enrollingcomprising providing a copy of the mobile device management profile tothe client device.
 12. The computer storage medium of claim 11, theoperations comprising: receiving a second request for access to a secondnetwork resource from the client device, the second request receivedprior to the first request and the second network resource correspondingto one of a plurality of unrestricted resources accessible by devicesnot enrolled with the mobile device management system; and allowing theclient device access to the second network resource.
 13. The computerstorage medium of claim 11, the operations comprising: receiving asecond request for access to a second network resource from the clientdevice, the second network resource corresponding to one of theplurality of restricted resources; determining whether the client deviceis enrolled with the mobile device management system; and allowing theclient device access to the second network resource based on determiningthat the client device is enrolled with the mobile device managementsystem.
 14. The computer storage medium of claim 13, the operationscomprising: determining whether the mobile device management profile hasbeen deactivated on the client device; and un-enrolling the clientdevice from the mobile device management system based on determiningthat the mobile device management profile has been removed from theclient device, the un-enrolling preventing the client device fromaccessing the plurality of restricted resources.
 15. The computerstorage medium of claim 13, wherein the plurality of restrictedresources comprises resources managed by an organization that uses themobile device management system.
 16. The computer storage medium ofclaim 13, wherein the plurality of restricted resources comprises publicnetwork resources.
 17. The computer storage medium of claim 11, whereindetermining that the client device is not enrolled with the mobiledevice management system comprises: determining whether a heartbeatsignal has been received within a predetermined period of time; anddetermining that the client device is not enrolled with the mobiledevice management system based on determining that the heartbeat signalhas not been received within the predetermined period of time.
 18. Thecomputer storage medium of claim 11, wherein determining that the clientdevice is not enrolled with the mobile device management systemcomprises: determining whether a device identifier associated with theclient device is categorized as being enrolled with the mobile devicemanagement system; and determining that the client device is notenrolled with the mobile device management system based on determiningthat the device identifier associated with the client device is notcategorized as being enrolled with the mobile device management system.19. The computer storage medium of claim 11, wherein: the instructionscomprise instructions for presentation of an agreement to enroll theclient device with the mobile device management system; and enrollingthe client device with the mobile device management system comprisesreceiving input from the client device indicating acceptance of theagreement, wherein the client device is enrolled with the mobile devicemanagement system in response to receiving the input from the clientdevice.
 20. The computer storage medium of claim 11, wherein determiningthat the client device is not enrolled with the mobile device managementsystem comprises: determining whether the client device is connected toa non-compliant network, the non-compliant network providing access to aplurality of unrestricted resources and not providing access to any ofthe plurality of restricted resources; and determining that the clientdevice is not enrolled with the mobile device management system based ondetermining that the client device is connected to the non-compliantnetwork.
 21. A system comprising: one or more computers and one or morestorage devices storing instructions that are operable, when executed bythe one or more computers, to cause the one or more computers to performoperations comprising: receiving a first request for access to a firstnetwork resource from a client device, the first network resourcecorresponding to one of a plurality of restricted resources accessibleonly by devices enrolled with a mobile device management system;determining whether the first request to access the first resourceincludes an address of a predetermined proxy server; determining thatthe first request to access the first resource does not include theaddress of the predetermined proxy server; determining that the clientdevice is not enrolled with the mobile device management system based ondetermining that the first request to access the first resource does notinclude the address of the predetermined proxy server; preventing, basedon determining that the client device is not enrolled with the mobiledevice management system, the client device from accessing the firstnetwork resource; providing to the client device, based on determiningthat the client device is not enrolled with the mobile device managementsystem, a redirect to a mobile device management resource that isdifferent from the first network resource; providing instructions forpresentation of a user interface to the client device, the providedinstructions relating to the mobile device management resource andcomprising a user notification regarding a mobile device managementprofile; and enrolling the client device with the mobile devicemanagement system, the enrolling comprising providing a copy of themobile device management profile to the client device.
 22. The system ofclaim 21, the operations comprising: receiving a second request foraccess to a second network resource from the client device, the secondrequest received prior to the first request and the second networkresource corresponding to one of a plurality of unrestricted resourcesaccessible by devices not enrolled with the mobile device managementsystem; and allowing the client device access to the second networkresource.
 23. The system of claim 21, the operations comprising:receiving a second request for access to a second network resource fromthe client device, the second network resource corresponding to one ofthe plurality of restricted resources; determining whether the clientdevice is enrolled with the mobile device management system; andallowing the client device access to the second network resource basedon determining that the client device is enrolled with the mobile devicemanagement system.
 24. The system of claim 23, the operationscomprising: determining whether the mobile device management profile hasbeen deactivated on the client device; and un-enrolling the clientdevice from the mobile device management system based on determiningthat the mobile device management profile has been removed from theclient device, the un-enrolling preventing the client device fromaccessing the plurality of restricted resources.
 25. The system of claim23, wherein the plurality of restricted resources comprises resourcesmanaged by an organization that uses the mobile device managementsystem.
 26. The system of claim 23, wherein the plurality of restrictedresources comprises public network resources.
 27. The system of claim21, wherein determining that the client device is not enrolled with themobile device management system comprises: determining whether aheartbeat signal has been received within a predetermined period oftime; and determining that the client device is not enrolled with themobile device management system based on determining that the heartbeatsignal has not been received within the predetermined period of time.28. The system of claim 21, wherein determining that the client deviceis not enrolled with the mobile device management system comprises:determining whether a device identifier associated with the clientdevice is categorized as being enrolled with the mobile devicemanagement system; and determining that the client device is notenrolled with the mobile device management system based on determiningthat the device identifier associated with the client device is notcategorized as being enrolled with the mobile device management system.29. The system of claim 21, wherein: the instructions compriseinstructions for presentation of an agreement to enroll the clientdevice with the mobile device management system; and enrolling theclient device with the mobile device management system comprisesreceiving input from the client device indicating acceptance of theagreement, wherein the client device is enrolled with the mobile devicemanagement system in response to receiving the input from the clientdevice.
 30. The system of claim 21, wherein determining that the clientdevice is not enrolled with the mobile device management systemcomprises: determining whether the client device is connected to anon-compliant network, the non-compliant network providing access to aplurality of unrestricted resources and not providing access to any ofthe plurality of restricted resources; and determining that the clientdevice is not enrolled with the mobile device management system based ondetermining that the client device is connected to the non-compliantnetwork.